Pull Request Template

📄 Description

This PR reverts the main branch to the last stable static version (d6d3b5f) of the Keploy API Fellowship website.

The recent migration to Next.js 15 (commit f05e802) caused the live deployment at [fellowship.keploy.io](https://fellowship.keploy.io) to fail with the following error:

404 Not Found
Code: NoSuchKey
Message: The specified key does not exist.
Key: index.html

The current deployment platform is configured for static file hosting, which expects an index.html entry point.
However, Next.js generates a different build output structure unless it’s statically exported (next export) or configured for SSR hosting.

To ensure the site remains accessible to users, this PR temporarily restores the last working HTML/CSS/JS version until deployment access and configuration updates are available.

🔒 The Next.js migration code has been safely preserved on a new branch:
revert-deployment

Fixes: (N/A or link the issue if one exists)

🧠 Type of Change

• Rollback (temporary revert to last stable release)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

✅ How Has This Been Tested?

• Verified that the reverted commit (d6d3b5f) builds successfully.
• Confirmed locally that all HTML, CSS, and JS assets render correctly.
• Deployment will automatically rebuild on merge, restoring the working version of the site.

📷 Additional Context

Next Steps:

• Update deployment configuration to support Next.js 15 (via next export, Vercel, or custom SSR setup).
• Once deployment access is restored, reintroduce the Next.js migration from the nextjs-migration-backup branch.

🧾 Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have tagged the reviewers in a comment below in case my pull request is ready for review
• I have signed the commit message with --signoff